home *** CD-ROM | disk | FTP | other *** search
- Path: access1.digex.net!not-for-mail
- From: ell@access1.digex.net (Ell)
- Newsgroups: comp.lang.c++
- Subject: Re: Pure Virtual Destructor Question
- Date: 10 Feb 1996 05:22:07 GMT
- Organization: The Universe
- Distribution: world
- Message-ID: <4fha1v$89v@news4.digex.net>
- References: <4fecq0$k4e@news4.digex.net> <4fg2s5$r02@cnn.exu.ericsson.se> <4fgp0o$759@news4.digex.net>
- NNTP-Posting-Host: access1.digex.net
- X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
-
- Ell (ell@access1.digex.net) wrote:
- : Mickey Williams 66753 (ebumow@ebu.ericsson.com) wrote:
- : : In article k4e@news4.digex.net, ell@access4.digex.net (Ell) writes:
- : :
- : : >Immediately above you are logically "defining" your "pure virtual"
- : : >destructor "inside the class where it is "declared" as a pure virtual
- : : >function. It is _illegal_ to logically, or physically "define" a pure
- : : >virtual function in the class it is "declared" in. A pure virtual should
- : : >only be defined in classes derived from the class where the pure virtual
- : : >is declared. Only derived classes should "do some destructor stuff".
- :
- : : This is not true in the case of pure virtual destructors. You must
- : : always provide a function body for a virtual dtor, even if it
- : : is pure.
- :
- : Another non-orthogonal, non-intuitive C++ ism. Oh well.
- :
- : Elliott
-
- Don't get me wrong, I like the power, oo virtuality, and flexibility of
- the language, and this makes it beautiful for many circumstances. But
- some things about it are non-orthogonal, and non-intuitive, though
- probably necessary due to its C roots.
-
- Elliott
-
-
-